Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
| Attribute | Value |
|---|---|
| Connector ID | NetskopeAISecOps |
| Publisher | Netskope |
| Used in Solutions | Netskopev2 |
| Collection Method | CCF Push |
| Connector Definition Files | NetskopeAISecOps_connectorDefinition.json |
| DCR Definition Files | NetskopeAISecOps_DCR.json |
| CCF Configuration | NetskopeAISecOps_dataConnector.json |
| CCF Capabilities | Push |
| Ingestion API | Log Ingestion API — CCF Push connectors use DCR-based Log Ingestion API |
| Microsoft Learn | View on Learn |
The Netskope AI SecOps connector pushes AI SecOps case and risk-scoring events (case lifecycle, investigation enrichment, and entity risk-score changes) directly into Microsoft Sentinel using the Codeless Connector Framework (CCF) Push pattern and the Azure Monitor Logs Ingestion API. Events are written to the NetskopeAISecOps_CL table; parse the Data column at query time with the NetskopeAISecOpsEvents function.
This connector ingests data into the following tables:
| Table | Transformations | Ingestion API | Lake-Only |
|---|---|---|---|
NetskopeAISecOps_CL |
✗ | ✓ | ✗ |
💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.
Resource Provider Permissions:
Custom Permissions:
⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.
1. Create ARM Resources and Provide the Required Permissions
This connector enables your Netskope tenant's AI SecOps module to push case and risk-scoring events directly to Microsoft Sentinel via the Azure Monitor Logs Ingestion API.
Clicking on "Deploy push connector resources" will trigger the creation of the NetskopeAISecOps_CL Log Analytics table and a data collection rule (DCR) and data collection endpoint (DCE). It will then create a Microsoft Entra app registration, link the DCR to it, and set the entered secret in the application. This setup enables Netskope to send AI SecOps events securely to the DCR using an Entra token.
Deploy push connector resources
2. Configure the event destination in the Netskope AI SecOps admin console
Copy the values below into the Outbound webhook for the Microsoft Sentinel destination in the Netskope AI SecOps admin console (Auth type: OAuth2 client credentials). The fields are listed in the same order as the webhook form. Refer to the Netskope Community guide for the console steps.
DataCollectionEndpointNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
[concat(environment().authentication.loginEndpoint, '{0}/oauth2/v2.0/token')]ApplicationIdNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
ApplicationSecretNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
https://monitor.azure.com/.defaultTenantIdNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
DataCollectionRuleIdNote: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.
Custom-NetskopeAISecOps_CLNOTE: The Token URL is generated for the Microsoft Entra authority of the Azure cloud this workspace is deployed in (commercial or Government), so copy it exactly as shown.
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊